STLC:
   STLC stands for 'Software Test Life Cycle'.
   It is an systemmatic process/approach to test the s/w. It starts from requirement collection and ends with quality deliverables.

Different phases in STLC:

1. Requirement Collection & creation of SRS doc
		|
		V
2. Understand the requirements OR system study.
		|
		V
3. Write the Test plan (written by QA Lead/ Sr. QA)
		|
		V
4. Identify the test scenarios for writing the test cases (Approach: Write high level scenarios)
Note: Test scenario: It is an end-to-end workflow in the given requirements/application.
		|
		V
5. Write test cases for all the test scenarios by applying "Test Case Design Techniques"
		|
		V
6. Create a RTM (Requirement Traceability Matrix) document. So that we can map all the requirements with the test cases
		|
		V
7. Test case review. All the written test cases will be sent to review. Usually review will be done in 2 cycles.
  (a) Internal Review (Done by BA, Dev, PEER etc)
  (b) External Review (Done by Customer)
		|
		V
8. QA should fix all the review comments, baseline the test case document and store them in the test case repository.
Note: 
1. Baseline means finalizing the docs by fixing all the errors/review comments.
2. Test Case Repository: It is a centralized location in which all the test cases are stored. 
Ex: ALM, SVN, git, Share Point, dedicated PC etc.
		|
		V
9. Whenever build comes, select the test cases as per the build scope (RN), provide the estimation & execute them against the build. During execution If you find any defects it should be logged against Dev in a defect tracking tools. (Bugzilla, ALM, TFS, JIRA etc)

						Execution
						
	(1) Manual Execution						(2) Automation Execution
			|											|
			V											V
	Passed	   Failed							Passed       Failed
	              |												|
				  V												V
			Analyse the failure							Analyse the failure by
			by rerunning the test                          rerunning the test script
			case											|
			      |                                         V
				  V									False      Actual
			False      Actual						Failure    failure
			failure    failure										|
						  |                                         V
						  V                                  Script        Actual s/w
					Log the defect                           issue         issue
					in defect tracking						   |			  |
					tool									   V			  V
														Fix the            log the  script   			defect		
														review->store
														in repo.
		|
		V
10. Prepare consolidated test execution report

Sample Consolidated Test Execution report must have following information:
1. Total # of test cases selected	: 120
2. Total # of test cases executed	: 70
3. Total # of test cases Passed		: 55
4. Total # of test cases failed		: 15
5. Total # of test cases blocked	: 0
6. Total # of test cases pending	: 50
7. Total # of defects logged		: 2

------ End of project from customer point of view----

But from company point of view, the team will attend the Retrospect meeting OR Project/Sprint closure meeting OR post-morton meeting:

Output of Retrospect meeting:
1. What are the best practicess we have followed
2. Any process which requires improvement.
3. Any challenges faced and how did you overcome.
4. Any suggestions

  The QA Manager/SM will document the retrospect discussions. So that the documentaion will act as a base for the next upcoming sprints.

